Communications distribution apparatus and method

ABSTRACT

A computer system and method for distributing, decisions in a network. The network is partitioned into multiple levels including a user interface level, a gateway level and a domain level. All attached devices in the network communicate either directly or indirectly with user interface unit. Several gateway systems are attached to the user interface level. Each gateway system has decision-making capability. Each gateway system has connected to it multiple domains. Each domain level again has a set of decision-making capabilities. When the domain level receives an input, the domain level decides whether or not it may react based upon its decision-making capabilities. The domain system may react to the input and provide the gateway with a report of the event and the domain system&#39;s reaction to it. Once the gateway system receives the event and domain system status, the gateway determines whether to react to this event. The gateway may react to this event and direct the domain system to act according to its predetermined programming. The gateway system then sends to the user interface system the event, the domain system status and the gateway system status. The status includes whether the domain or gateway systems have reacted to the event. At the user interface level, the user interface system determines whether to react to this event and then provides a notice to the user, which allows the user to input an action.

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] Not Applicable.

STATEMENT REGARDING FEDERALLY SPONSORED RESEARCH OR DEVELOPMENT

[0002] Not Applicable

FIELD OF THE INVENTION

[0003] The field of the invention relates to a hierarchical networkingstructure for a computer-implemented security system, including videocameras, VCRs, locks, alarms and other security devices.

BACKGROUND OF THE INVENTION

[0004] For many years individuals have used computer systems to dorepetitive, mathematic intensive calculations. Computer systems havebeen able to do basic elemental decision-making based upon apredetermined response to a given set of criteria. As computer systemshave proliferated throughout society, computer systems of various levelsof capabilities have developed. Highly advanced computer systems withpowerful decision making tools are available as are machines with just afew basic computer decision-making skills. Further, a wide variety ofcomputer systems or machines with computing capability are availablewith varying degrees of decision-making capabilities. However, onerecurring theme appears; that the decision-making capability in anetworked system has been centralized in one advanced computer system.These networks which center around one powerful decision-making computersystem are provided in many different hierarchies, examples of which areshown in U.S. Pat. No. 5,995,916 entitled “Process Control System forMonitoring and Displaying Diagnostic Information of Multiple DistributedDevices” issued to Nixon et al and U.S. Pat. No. 5,886,894 entitled“Control System for Automated Security and Control Systems” issued toRakoff.

[0005] Further, security systems of varying degrees of intelligence havebeen available for many years. Basic security systems are available withlimited decision-making capabilities and are even available with nodecision-making capabilities, just relays. An example of this is a dooralarm attached to a speaker. Once the door alarm contact is broken, thespeaker provides an audible output signaling that the door has beenopened. However, more sophisticate˜systems have become available andsecurity elements have evolved with differing levels of decision-makingcapabilities. However, the decision making capabilities in thesesecurity systems exist in a centralized computer system. Therefore, in asecurity system computer network, multiple layers of security devicesand computing systems may be attached, however the attached computersystems and security system devices report inputs they receive to thecentralized computer system and receive instructions from thecentralized computer without implementing individual decision-makingcapabilities. U.S. Pat. No. 5,995,916 discloses a system in which amain, controlling decision-making computer system has attached to itseveral controller computer systems that are further attached to aplurality of field devices. The field devices report occurrences ofinputs they receive to the controller computer system. The controlroutines configure the data and pass it up to a main controller computersystem. The main controller computer system then provides output to thecontrolling systems. The controlling systems then configure thisinformation so it can be sent to the field devices. As can be seen, thishierarchical system allows for raw data to be passed from the bottom upto the decision-making computer system and then allows for thedecision-making computer system to pass instructions down to the fielddevices. A second hierarchical structure is shown in U.S. Pat. No.5,886,894. In this system, a main computer decision-making system isdisclosed with a master unit connected to several slave units. This iscommonly referred to as a wagon wheel hierarchy. The slave units receiveinputs and pass these inputs into the main computer decision-makingsystem. The computer decision making system obtains all the inputs fromthe multiple slave units and then based upon its decision-makingcapabilities sends instructions out to the various slave units. However,the decision-making capabilities for both of these systems reside in acentralized location. Therefore, any advancement in the ability todistribute the decision-making process throughout the computer securitysystem network would be advantageous.

SUMMARY OF THE INVENTION

[0006] A computer system and method for distributing decisions in anetwork. The network is partitioned into multiple levels including auser interface level, a gateway level and a domain level. The userinterface system allows a user to participate in the decisions andcontains a large mass storage capability. All attached devices in thenetwork communicate either directly or indirectly with user interfacesystem. Several gateway systems are attached to the user interfacesystem. The gateway systems contain the majority of the decision-makingcapabilities. The gateway systems also have the ability to provideinputs and outputs based on the inputs provided to it. Each gatewaysystem has connected to it multiple domain systems. Each domain systemhas a reduced set of decision-making capabilities, however, each domainsystem has the ability to react to a series of inputs without receivinginstruction from the gateway system. When a domain system receives aninput, the domain system determines whether it may react based upon itsdecision-making capabilities. If it may, then the domain system reactsto the input and provides the gateway system with a report of the eventand the domain system's reaction to it. Once the gateway system receivesthe event and status of the domain system, the gateway system determineswhether it has the capability to react to this event. If the gatewaysystem has the capability to react to this event, then it directs one ormore of the domain systems according to its predetermined programming.The gateway system then passes to the user interface system the event,the domain system's status and the gateway system's status. The statusesinclude whether the domain or the gateway systems have reacted to theevent. At the user interface level, the user interface system determineswhether it has the capability to react to this event and then provides anotice to the user and allows for the user to input any action in whichthe computer system is to take.

A BRIEF DESCRIPTION OF THE DRAWINGS

[0007] A better understanding of the present invention can be obtainedwhen the following detailed description of one exemplary embodiment isconsider in conjunction with the following drawings, in which:

[0008]FIG. 1 is a block diagram depicting the computer system accordingto the invention;

[0009]FIG. 2 is a block diagram depicting the user interface systemaccording to the invention;

[0010]FIG. 3 is a block diagram depicting the gateway system accordingto the invention;

[0011]FIG. 4 is a block diagram depicting the domain system according tothe invention;

[0012]FIG. 5 is a block diagram of an intelligent field device accordingto the invention; and

[0013] FIGS. 6A-6D are flow diagrams of the distributed decision-makingprocess.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

[0014] In the description that follows, like parts are marked throughoutthe specification and drawings with the same reference numerals,respectively. The drawing figures are not necessarily drawn to scale andcertain figures may be shown in an exaggerated or generalized form ininterest of clarity and conciseness.

[0015]FIG. 1 illustrates the block diagram of the computer systemaccording to the present invention. A user interface system 100 isshown. The user interface system 100 is of the kind generally availableto individuals or organizations that need network servers. The userinterface system 100 is connected to multiple gateway systems 102 a, 102b through 102 z via communication lines 122 a, 122 b through 122 zrespectively. Communications lines 122 are preferably a standardtelephone or direct communication line. Each gateway system 102 athrough 102 z is connected to multiple domain systems 104 a through 104z, 106 a through 106 z and 108 a through 108 z, respectively. Thegateway systems 102 a through 102 z are connected to domain systems 104a through 104 z, 106 a through 106 z and 108 a through 108 z viacommunications lines 124 a through 124 z, 126 a through 126 z and 128 athrough 128 z respectively. Each domain system 104 a through 104 z, 106a through 106 z and 108 a through 108 z are connected to field systems110 a, 110 b through 110 z, 112 a, 112 b through 112 z, 114 a, 114 bthrough 114 z, 116 a, 116 b through 116 z, 118 a, 118 b through 118 zand 120 a through 106 z and 108 a through 108 z are connected to thefield systems 110 a through 110 z, 112 a through 112 z, 114 a through114 z, 116 a through 116 z, 118 a through 118 z and 120 a through 120 zthrough communication lines 130 a through 130 z, 132 a through 132 z,134 a through 134 z, 136 a through 136 z, 138 a through 138 z and 140 athrough 140 z respectively. Decision making capabilities exist in alllevels of the system. Information flows from the field systems level upthrough the domain systems level, through the gateway system level tothe user interface system level and commands or instructions flow fromthe user interface system level through the gateway system level to thedomain system level to the field system units. For example, if a sensoris activated in field system unit 114 b, the field system unit 114 bdetermines if the field system unit 114 b may react due to the sensorinput or event. If the field system unit 114 b has been programmed torespond to this particular input, then the field system unit 114 b willcause an action to be performed. Regardless of whether field system unit114 b reacts to the sensor input, the event and the field system 114 bstatuses are transmitted via the communication line 134 b to the domainsystem 106 a. The domain system 106 a determines if the domain system106 a may react to the sensor input received at the field system 114 b.The domain system 106 a may respond by directing the field system 114 bto react or may cause one or more other field system 114 a, 114 cthrough 114 z under its control to react; for “ample, sending a commandto field system 114 a. Then, the domain system 106 a sends notice of theevent, the status of the Field systems 114 a through 114 z, and thestatus of domain system 106 a to gateway system 102 b via communicationline 126 a. At the gateway system 102 b, the gateway system 102 bdetermines whether an action is required based upon the informationreceived from the domain system 106 a. The gateway system 102 b mayreact by providing a command to domain system 106 a, which is thenpassed on to any of the field systems 114 a through 114 z. Further, thegateway system 102 b may send a command to domain system 106 z viacommunication line 126 z to command any of the field units 116 a, 116 bthrough 116 z to react in a certain way. Then the gateway system 102 bnotifies the user interface system 100 through communication line 112 bof the event, the field systems status, the domain systems status andthe gateway system status. Thus, the decision-making capability isdistributed through the multiple layers.

[0016] Referring now to FIG. 2 a block diagram of the user interfacesystem is shown. The user interface system 100 includes an input device200 which further includes a mouse 202 and a keyboard 204. The inputdevice 200 is connected via a bus 228 to an output device 206. Theoutput device includes a visual device 208 and an audio device 210. Theoutput device 206 is connected via the bus 228 to a processor 212.Further, a memory system 214 is connected to the bus 228 and includes aRandom Access Memory (RAM) 216 and a Read Only Memory (ROM) 218. Anetworking device 226 is connected to the bus 228. A mass storage system220 is connected to the bus 228 and includes a hard disk drive system222 and a Read/Write CD 224. The user interface system 100 is typicallya server-based system which is commonly available through manufacturerssuch as Dell Computer Corporation. The user interface system 100, in onedisclosed embodiment, is shown as a single computing machine, however,multiple machines of varying capabilities may be included withoutdeparting from the spirit of the invention. The visual device 208typically includes a computer monitor and may include other devices suchas warning lights. The audio device 210 typically includes a speakersystem common to computer systems; however, other devices such as bellsor whistles may be used without distracting from the spirit of theinvention. The input devices can include a bar card readers or scannersand may be implemented without departing from the spirit of theinvention. The mass storage system 220 may further include an opticalstorage device or tape devices for storage of large amounts of data. Theuser interface system 100 may be designed such that all data messagesreceived from any device are stored in the: mass storage devices and allcommands sent from the user interface system may also be stored in themass storage system. The speed and size of the mass storage system mayvary depending on the specific needs of a customer. However, differentsizes and types of the mass storage system 220 may be implementedwithout departing from the spirit of the present invention.

[0017] The user interface system 100 includes hardware and softwareresident in the hardware. This software allows the user interface system100 to automatically respond to certain events received at the userinterface system 100 or allows the user interface system 100 to prompt auser for a command, and then once a command has been received, to passthe command down to the gateway systems 102 a through 102 z. An exampleof an event in which the user interface system 100 automaticallyresponds is if an entry request is received from the gateway system 102b identifying a particular individual swiping an identification card.The user interface system 100 software then compares that entryidentification to information stored in the mass storage system 220 todetermine if that individual can be granted access. If the individualhas access rights, then the command to allow entry is sent from userinterface system 100 to the gateway system 102 b. However, if theindividual's entry identification is not present in the user interfacesystem 100 mass storage system 220, then the user may be prompted, viathe output device 206, to request entry of the individual. The user mayenter a command through the input device 200 which is sent from the userinterface system 100 to the gateway system 102 b to command entry of theindividual. As was discussed, the user interface system 100 may includeseveral computing systems with varying functions. The user interfacesystem 100 may include computing systems designed for storage of largescale databases; while: other computing systems of the user interfacesystem 100 may be designed for the rapid input and output of data to theuser. The mass storage system 220 may also include backup devices whichallow for the databases and any other software and data within userinterface system 100 to be backed up on a separate physical medium incase of a computer malfunction. Further, the configuration data for alldevices of the security system may be stored in the mass storage system220 of the user interface system 100 and be accessible duringinitialization of any of the devices, including the devices at thegateway system level, the domain system level and the field systemlevel. The controlling and decision-making software (not shown in thedrawings) is resident in either the mass storage system 220 or thememory system 214 of the user interface system 100 and is executableupon initialization or manually by the user.

[0018] Referring now to FIG. 3, a block diagram of the gateway system isshown. An exemplary gateway system 102 is shown including a processor300 connected via a bus 310 to a network device 302, a memory system 304and a mass storage system 312. The memory system 304 includes a RAM 306and a ROM 308. The mass storage system 312 includes a hard disk drive314 and a Read/Write CD 316. The gateway system 101 typically is apersonal computer system available to an individual user or it can be acomputer server typically available to businesses. The gateway system102 may include input and output devices allowing for a user to makedirect communication to the gateway system 102, however, in thisdisclosed embodiment they are not shown. The input and output deviceswould allow a user to directly access the gateway system 102 formaintenance and initialization. A computer program or software (notshown) is resident in either the memory system 304 or the mass storagesystem 312. The computer program is activated when the gateway system102 is initiated or upon a command from the user interface system 100.The computer program allows for the gateway system 102 to receive eventsfrom the computer systems at the domain level, possibly react to theevent, send information to the user interface system 100 and receivecommands from the user interface system 100. If an event is outside ofthe programmed capabilities of the a gateway system 102, then thegateway system 102 does not react other than to notify the userinterface system 1001 of the event and the gateway systems 102 status.Further, if the gateway system 102 responds to the event, then thestatus of the gateway system 102 is sent to the user interface system100.

[0019] In one embodiment, the gateway system 102 includes the majorityof the decision-making capability. This decision-making capability isresident in the gateway system 102 hardware and software resident in thememory system 304 or the mass storage system 312. By providing thedecision-making capability in this lower level computer system, thespeed of the decision-making is greatly increased. For example, if anindividual wishes to enter a building, the individual may slide an entrycard through a card reader. In the prior art, the identification of theindividual would be sent up through the different levels to thecentralized computer. The centralized computer would then compare therequested individual's identification stored in the centralized computerto determine if a match has occurred then, the centralized computerwould send the instructions back down through the levels to the entrypoint and either allow or not allow the individual to enter. In thepresent invention, the decision-making capability is moved from thecentralized computer to one of the computer systems closer to the eventpoint. If an individual wishes to enter a building and slides anidentification card through an 10 identification card reader, theidentification request may be sent up through the field system 110 tothe domain system 104 to the gateway system 102. The gateway system hasthe capability to store individual identification data in its massstorage system 312 and may have the decision-making capability todetermine whether to allow entry of this individual. Therefore, the stepof passing this information up to the user interface system 100 isremoved and the decision to allow entry of the individual can be made atthe gateway system 102. This advantage is further amplified by allowingthe decision making capabilities to be dispersed and distributed to thedomain systems level and the field systems level, depending upon thecapabilities of the specific systems. Thus, if the field system 110includes a small mass storage device which includes the identificationof a few users, the individual wishing to have entry may have hisidentification stored at the field system 110 and thus have immediateaccess without the necessity to pass the request up through the varyinglevels of the security system network. However, if an individual'sidentification is not contained in the lower level computing systems,then the request is passed up to the next higher level to determine ifthe event can be handled at that level. Another advantage of this systemis redundant wiring, as it is commonly shown in the prior art, isunnecessary. When the lower level computing systems maintain decisionmaking capabilities, then a disconnection of the lower level systemsfrom the central computing system will not stop all activity at thelower level computing systems. In the present invention, the lower levelcomputing systems can continue to function on their limiteddecision-making ability. Not all events can be handled as each lowerlevel system is limited to its capabilities, however, the lower levelcomputing systems will continue to function at some level. Further, inthe present invention, when communication between the multiple levels isreestablished, all events that have occurred while the lower levelsystems have been disconnected from the user interface system 100 aresent through the multiple levels as is disclosed herein and thus theuser interface system 100 is able to maintain an accurate and reliableevent status log of all events that have occurred, even if the userinterface system 100 was not directly communicating with all lower levelcomputer systems throughout the period in question.

[0020] Referring now to FIG. 4 a block diagram of the domain system isshown. An exemplary embodiment of the domain system 104 includes aprocessor 400 connected via a bus 404 to a networking device 402, amemory system 406 and a mass storage system 412. The memory system 406includes a RAM 408 and a ROM 410. The mass storage system 412 includes ahard disk drive 414 and a Read/Write CD 416. The domain system 104includes software resident in the memory system 406 or the mass storagesystem 412 that is executed upon initiation of the domain system 104 orupon command from the gateway system 102. The software includesdecision-making capabilities. Thus, when the domain system 104 receivesan event or an input, the domain system 104 evaluates the event againstits preprogrammed list of options. If the event is an event in which thedomain system 104 can respond, then domain system 104 reacts to theevent. Next, the domain system 104 will send the event and the status ofthe domain system 104, whether or not the domain system 104 responded tothe event, to the gateway system 102 via the networking device 402. Thedomain system 104 may be connected to multiple field system leveldevices or the domain system 104 may be the lowest level device in thenetwork. Thus, the domain system 104 may be an intelligent field unit,such as scanning unit.

[0021] The domain system 104 typically includes a subset of capabilitiesfrom the gateway system 102. The domain system 104 may include a smallermass storage system 412 and slower or less capable processors 400.Typically, the processor 400 of the present invention includes eight (8)bit and sixteen (16) bit processors.

[0022] Referring to FIG. 5, a block diagram of an intelligent fieldsystem is shown. The intelligent field system 110 includes a processor512 connected via a bus 516 to a networking device 514, a memory system518, and a mass storage system 524. The memory system 518 includes a RAM520 and a ROM 522. The mass storage system 524 includes a hard diskdrive 526 and a Read/Write CD 528. The intelligent field system 110includes software resident in the memory system 518 or the mass storagesystem 524 that is executed upon initialization of the intelligent fieldsystem 110 or upon command from the domain system 104. The softwareallows the field system 110 to sense an event, and if the event iswithin a preprogrammed capability list, to respond to that event beforesending the event and field system status to the domain system 104.

[0023] The intelligent field systems 110 include fingerprint readers,card readers, video recorders, video cameras, scanners, and a variety ofother security devices, all of which may implemented without departingfrom the spirit of the invention. The field system 110 may also includedevices which are labeled non-intelligent. Such devices would includelocks, alarms, motion detectors, and other devices which do not requirecomputing capability to function. Such devices, when implemented, do notdetract from the spirit of the invention. When non-intelligent fieldsystems 110 are implemented, then the output from these non-intelligentfield systems 110 is sent to the domain system 104 when the eventoccurs.

[0024] FIGS. 6A-6D show a flow diagram of the distributeddecision-making process. The process begins with start 600. Next, instep 602, the field systems, domain systems, gateway systems, and theuser interface systems are initialized. During the initializationprocess, the software resident in these systems is executed.Alternatively, the user can command execution of the software afterinitialization. In step 604, the field systems, domain systems, gatewaysystems, and user interface systems begin monitoring for an event. Anevent includes any input into the field system or the domain system ifthere are no field systems attached to the domain system. For instance,an event may be the activation of a sensor, a door being opened, thesliding of a card through a card reader or an alarm if the motiondetector detects motion. Next in step 606, a field system receives anevent. The field system then determines if it has decision-makingcapability in step 608. If there is no decision-making capability in thefield system, then the process continues with step 614. If the fieldsystem is an intelligent unit, as determined in step 608, then the fieldsystem determines if the event received is addressable by the fieldsystem in step 610. If the event is not addressable by the field system,then the process continues to step 614. If the event is addressable bythe Field system in step 610, then the Field system addresses the eventin step 612. Next, in step 614, the notification of the event and thestatus of the field system are sent to the domain system. The event andthe field system status are sent to the domain system regardless ofwhether the field system has addressed the event. Thus, the event andthe status of the field system are always sent to the domain system uponreceipt of an event. In step 616, the domain system receives the eventand the field system status. The domain system determines whether thedomain system may react and address the event in step 618. If the domainsystem is capable of addressing the event, then the domain system sendsinstructions to field system in step 620. Next in step 622, the domainsystem sends the event, field system status and the domain system statusto the gateway system. This step is done regardless of whether thedomain system reacted to the event. In step 624, the gateway systemreceives the event, field system status and domain system status. Thegateway system 15 determines if it is capable of addressing the event instep 626. If yes, then the gateway sends instructions to the domainsystem and possibly to the field systems through the domain system instep 628. If no, then the event, field system status, domain systemstatus and gateway system status are sent to the user interface systemin step 630. Again, this step is implemented regardless of whether thegateway system reacted to the event. Next, in step 632, the userinterface system receives the event, field system status, domain systemstatus, and gateway status. In step 634 the user interface systemdetermines if it is capable of addressing the event. If yes, then theuser interface system sends instructions to the gateway system andpossibly the field system and domain system. In step 638, the userinterface system prompts the user for input. Next, in step 640, the userinterface system determines if the user has provided any input. If yes,then the user's instructions are sent to the gateway system and possiblythe field systems and domain systems in step 642. Next, in step 644, theevent, field system status, domain system status, gateway status anduser interface status are stored in user interface system's mass storagesystem. The process ends in step 646.

[0025] In one embodiment of the present invention, the varying levels ofthe network are not limited to responding only to the lower leveldevices that sent the event. For example, the domain system 104 a mayreact to an event from field system 110 a by commanding field system 110c to commence operation. Further, the gateway system 102 a may react toan event transmitted by domain system 104 b, by directing domain system104 x to direct a field unit under that domain system to commence anaction. Further, the user interface system 100 may react to the sameevent by commanding different gateway system to react.

[0026] The foregoing disclosing the description of the invention areillustrative and explanatory thereof and various changes to size, shape,material, components, and order may be without departing from the spiritof the invention.

What is claimed is:
 1. A method of distributing decisions in a networkincluding a user interface level, a gateway level, and a domain level,the method comprising the steps of: receiving data at a domain in thedomain level; deciding at the domain if the domain is to react; reactingto the data or sending the data to a gateway in the gateway level;deciding at the gateway if the gateway is to react; reacting to the dataor sending the data to a user interface in the user interface level;deciding at the user interface if the user interface is to react; andreacting to the data or not reacting to the data.
 2. The method of claim1, wherein the step of the domain receiving data at the domain levelincludes receiving data from a field device.
 3. The method of claim 2,wherein the step of the domain reacting to the data includes providinginstructions to the field device.
 4. The method of claim 1, wherein thestep of the gateway reacting to the data includes providing instructionto the domain.
 5. The method of claim 1, wherein the step of the userinterface reacting to the data includes providing instructions to thegateway, wherein the gateway then provides instructions to the domain.6. The method of claim I further comprising the step of storing the datain the user interface level.
 7. The method of claim I further comprisingthe steps of sending the data and the decision to react to the gatewayif the domain reacts; sending the data and the decision to react to theuser interface if the gateway reacts.
 8. The method of claim 1, whereinthe step of the user interface deciding to react includes: outputtingthe data to a user; and receiving input from the user.
 9. The method ofclaim 1, wherein the step of the user interface not reacting to the dataincludes storing the data.
 10. The method of claim 2, wherein the stepof receiving data from the field device includes receiving data from atleast one field device.
 11. The method of claim 10, wherein at least onefield device is a plurality of field devices.
 12. The method of claim 1,wherein the step of the gateway receiving data from the domain includesreceiving data from at least one domain.
 13. The method of claim 12,where at least one domain is a plurality of domains.
 14. The method ofclaim 1, wherein the step of the user interface receiving data from thegateway includes receiving data from at least one gateway.
 15. Themethod of claim 14, wherein at least one gateway includes a plurality ofgateways.
 16. A security system on a network of at least three levelscomprising: a user interface system, wherein the user interface systemincludes a processor, a user input device, a user output device, amemory system and a networking device; a gateway system connected to theuser interface system through the network, the gateway system includinga processor, a memory system and a networking device; a domain systemconnected to the gateway system through the network, the domain systemincluding a processor, a networking device, a memory system, an outputdevice and an input device; software resident in the user interfacesystem, the software when executed performing the steps of: receivingdata from the gateway system; deciding to react; and reacting to thedata or not reacting to the data software resident in the gatewaysystem, the software when executed performing the steps of: receivingdata from the domain system; deciding to react; and reacting to the dataor sending the data to the user interface system; software resident inthe domain system, the software when executed performing the steps of:receiving data; deciding to react; and reacting to the data or sendingthe data to the gateway system.
 17. The security system of claim 16further comprising a field system connected to the domain system throughthe network.
 18. The security system of claim 17, wherein the domainsystem software steps of receiving data includes receiving data from thefield system.
 19. The security system of claim 17, wherein the fieldsystem includes a field system with a processor and a network device.20. The security system of claim 17, wherein the field system includesfield system with a sensor.
 21. The security system of claim 17, whereinthe field system includes a sensing device hardwired to the domainsystem.
 22. The security system of claim 16, wherein the user interfacesystem includes a user interface system with a mass storage device. 23.The security system of claim 22, wherein the user interface systemsoftware step of not reacting to the data includes storing data in themass storage device.
 24. The security system of claim 16, wherein thegateway system includes a gateway system with a mass storage device. 25.The security system of claim 16, wherein the domain system includes adomain system with a mass storage device.